Rewrite Search #1229
Merged
Rewrite Search #1229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hennevogel
force-pushed
the
refactoring/repomod
branch
from
92e2a08 to
a34abec
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
hennevogel
force-pushed
the
refactoring/repomod
branch
from
a34abec to
81b7f80
Compare
hennevogel
force-pushed
the
refactoring/repomod
branch
from
81b7f80 to
bf905db
Compare
Enable CI on staging branch
hennevogel
force-pushed
the
refactoring/repomod
branch
from
bf905db to
d9e5a5a
Compare
Also setup haml-lint TODO file
Require haml-lint to run in CI
Also moves docker base image build into OBS
All the stuff we need for what's to come...
A Distribution has many Repository A Repository has many Packages A Package has many Versions A Package has many Categories ActiveJobs are in the database too.
hennevogel
force-pushed
the
refactoring/repomod
branch
15 times, most recently
from
df61240 to
4500f27
Compare
hennevogel
force-pushed
the
refactoring/repomod
branch
6 times, most recently
from
02cd1a7 to
f4c1eef
Compare
With this we get a Distribution with a bunch of Repository in the database that you can sync. Which will create, per Distribution/Repository, a gazillion Package objects with data from primary, appdata and updateinfo. The user workflow will be as following: - As an admin I setup Distribution and it's repositories - As an admin I sync a Distribution's repositories to the database - As a user I search for Package of a Distributions in it's repositories - As a user I extend the search to packages build on OBS for this Distribution (not implemented here) Separating the Distribution "repository" search from searching through OBS will hopefully make more clear for newbies that enabling extra repos is kind of dangerous.
and regenerate TODO file...
Using dentarg/postgres
hennevogel
force-pushed
the
refactoring/repomod
branch
from
f4c1eef to
0aace9f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this we get a Distribution with a bunch of Repository in the database that
you can sync. Which will create (per Distribution/Repository) a gazillion
Package objects with data from primary, appdata and updateinfo.
The user workflow will be as following:
Separating the Distribution "repository" search from searching through OBS will
hopefully make more clear for newbies that enabling extra repos is kind of
dangerous.
TODO:
Package.iconsfromappdata-icons.tar.gzwithActiveStorage@distribution.packages.where(appstream: true)) by category.OBSclassOnce we have User we can also think about other stuff like comments, likes, ratings or whatnot.